Talk:Widget engine

confusing

I'm not sure what the second sentence of this extract means:

Usually these little applications resemble the tiny freeware apps that were developed by enthusiasts during the 80s. However, we must also point out that the majority of widgets are free and therefore its innovative approach and update may be quite limited.

Yeah, honestly, I was just wondering about that sentence myself. Someone should scrap that entirely if no one cleans it up (I think I'll come back in a few days and give it a shot myself if no one else feels like it). (edit: oops, I wasn't signed in, heh). --Phil Urich 06:19, 30 January 2007 (UTC)[reply]

I went ahead and removed it. Innovation is not related to price. --PrePressChris 17:27, 23 February 2007 (UTC)[reply]

Tafri

From what I can tell, the Tafri notes strewn through the article were spam. Their "engine" doesn't support widgets. It's just a program. There is nothing even remotely "widgety" about it. I've gotten rid of this spam altogether.

SuperKaramba?

Would it be okay to add a bit about SuperKaramba, seeing as it is a definite Widget engine, and quite popular with extensions on KDE-Look.org? Just wondering, since its Wikipedia page links to this one, but not vice-versa. T3thys::ben 17:49, 1 July 2007 (UTC) UPDATE: Okay, so I added it -- I didn't realize I was logged out at the time. (Sorry!) T3thys::ben 17:49, 1 July 2007 (UTC)[reply]

Online equivalent?

What is the online equivalent of a widget engine (i.e., a widget engine for widgets that are meant to be used online, on personal websites, blogs, etc.)? Should this article be broadened in scope to include such widgets? SharkD (talk) 03:22, 5 December 2007 (UTC)[reply]

List of external link

I understand that the list of external links has been removed because it seems to be too close to a list of commercial links. However, there was soome more general articles on this list, including the "what is a mobile widget" article on my blog, and a couple of others.... —Preceding unsigned comment added by Tomsoft (talk • contribs) 10:14, 16 April 2008 (UTC)[reply]

Opera

Prime example? —Preceding unsigned comment added by 86.159.63.60 (talk) 21:10, 4 June 2008 (UTC)[reply]

It is claimed that Opera was the first to support the standard. This is not true. Opera to date does not support the standard at all. —Preceding unsigned comment added by 84.215.160.79 (talk) 00:06, 7 January 2010 (UTC)[reply]

Eh... yes, Opera does in fact support it. The line is referenced. Unless you're aware of another engine that adopted the draft standard before Opera, which I doubt given that it is so new. _ɹəə pıɔnı 16:48, 7 January 2010 (UTC)[reply]

Widget History

The concept of small single-purpose applications is probably as old as windowing systems themselves. Consider the xclock and xeyes applications on the X Window System, or similar applications in the Smalltalk environment. The addition of internet content to widgets apparently came later, with the general availability of internet content (i.e. the Web). So internet content on its own wouldn't be a defining characteristic of desktop widgets. 68.8.65.163 (talk) 15:02, 26 September 2008 (UTC) —Preceding unsigned comment added by 68.8.65.163 (talk) [reply]

BeOS Replicants

BeOS had replicants[1] like a decade ago, likely even before Active Desktop. It was much wider than just putting a browser in the desktop, but also OLE/COM-like, enabling applications to embed others. One of BeOS applications, BeHappy[2], embedded the NetPositive browser to display documentations. It has been updated recently to use the NetSurf browser[3] for Haiku. —Preceding unsigned comment added by Mmu man (talk • contribs) 16:41, 21 October 2008 (UTC)[reply]

Adobe AIR

Would anyone here consider Adobe AIR to be a widget engine since an Adobe AIR app can be developed using Javascript? —Preceding unsigned comment added by LemChops (talk • contribs) 09:11, 20 November 2008 (UTC)[reply]

The Opera Widget engine (noted here already) seems to be aiming to directly compete with Adobe AIR in some ways in its latest incarnation. So there could be scope for this I supppose. It depends where exactly you draw the line between "desktop widget" and "desktop application". Then again if you did included Adobe AIR, you might be blurring the lines between Widget Engine and RCP, which would involve including Netbeans and the like.

I'm not really sure what exactly the strict definition of either is, so... _ɹəə pıɔnı 16:58, 7 January 2010 (UTC)[reply]

Grammar

"Mobile widgets can maximize screen space use"

Umm ... shouldn't mobile widgets be designed to minimise their screen space use?

Eh.. no. They should maximise their usage of the very limited space available. _ɹəə pıɔnı 17:24, 7 January 2010 (UTC)[reply]

Widgets is not yet a standard

Just a few points. The w3c widgets "standard" is not yet a standard (as it has not reached recommendation status). Is it ok to change to "widget specification". Also, I dropped the version number from widgets (i.e., the 1.0 is gone, as widgets will be standardized in levels, not versions). — Preceding unsigned comment added by Marcoscaceres (talk • contribs) 10:53, 29 May 2011 (UTC)[reply]